Systems and methods for on demand local commerce

ABSTRACT

Systems and methods for on demand local commerce are described. One example embodiment includes a device gathering location information and product interest associated with clients and client devices. The system may use location information in determining that the first plurality of client devices are within a first geographic area during a first time period, and may further use the interest information in calculating an interest level for a first product. A threshold may be identified and used in determining that the interest level for the first product exceeds the threshold. When the calculated interest level exceeds the threshold, a local commerce action is initiated. In various embodiments, the local commerce action may be a live on demand auction at a particular location, an offer associated with a geofenced area, a sales location recommendation to a merchant, or any other such local commerce action.

CLAIM OF PRIORITY

This Application is a continuation of U.S. application Ser. No.16/437,864, filed Jun. 11, 2019, which is a continuation of U.S.application Ser. No. 14/530,527, filed Oct. 31, 2014, each of which ishereby incorporated by reference in its entirety.

TECHNICAL FIELD

This application relates generally to geofencing, live auction systems,and local commerce within a network-based system operating over adistributed network with networked mobile devices, and more specificallyto systems and methods for automatically deploying on demand liveauctions and local commerce in response to analysis of client locationand interest data.

BACKGROUND

The ever increasing use of smart phones with data connections andlocation determination capabilities is slowly changing the way peopleinteract, shop for products and services, and manage accounts. Smartphones can provide clients with nearly instant information regarding awide range of information, such as product availability, pricing, orlocations of friends. Smart phones also commonly include mechanisms,such as global positioning system (GPS) receivers, that allow thedevices to constantly update location information. These technologychanges are also driving changes in the way merchants interact withcustomers.

BRIEF DESCRIPTION OF THE DRAWINGS

Some embodiments are illustrated by way of example and not limitation inthe figures of the accompanying drawings in which:

FIG. 1 is a block diagram depicting a system for on demand localcommerce and local auctions, in accordance with one example embodiment.

FIG. 2 illustrates a flow diagram on demand local commerce, inaccordance with one example embodiment.

FIG. 3 illustrates a method for on demand local commerce, according toanother example embodiment.

FIG. 4 illustrates a system that may be used to enable on demand localcommerce in certain example embodiments.

FIG. 5 illustrates aspects of a system that may be used for localcommerce in certain example embodiments.

FIG. 6 illustrates a mobile device that may be used with certain exampleembodiments of local commerce described herein.

FIG. 7 is a block diagram illustrating a network-based system for localcommerce, according to an example embodiment.

FIG. 8 is a block diagram illustrating geofencing modules that may beused with local commerce systems, according to an example embodiment.

FIG. 9 is a diagram illustrating aspects of local commerce, according toone example embodiment.

FIG. 10 is a diagrammatic representation of a machine in the exampleform of a computer system within which a set of instructions for causingthe machine to perform any one or more of the methodologies discussedherein may be executed.

DETAILED DESCRIPTION

Example systems and methods are described for using geofencing andcustomer interest information to implement live auction and localcommerce within a network-based system operating over a distributednetwork with networked mobile devices. In particular, exampleembodiments show systems and methods for automatically deploying ondemand live auctions and other such local commerce actions in responseto analysis of client location and interest data.

For example, in one embodiment, an art gallery may have a painting forsale by a local artist. The art gallery may provide geofencing andproduct interest threshold information to a local commerce server. Thegeofencing threshold information may define one or more geographic areasincluding a public park near an art gallery location. The productinterest threshold information may define an interest level frompotential clients that will be used to trigger a local commerce actionor message.

Clients may have an application operating on their devices that provideslocation information to the local commerce server. Additionally, theclients may provide interest information to the local commerce serverthrough a registration process or via the application. The localcommerce server gathers location information and interest informationand compares this to the threshold information received from the artgallery. If, for example, 15 devices are identified within the geofencedarea and 8 of the devices have expressed an interest in art auctions forlocal artists, the local commerce server may automatically initiate alive auction for the painting. The local commerce server may then notifythe art gallery that the threshold conditions have been met for anauction. The local commerce server may then also message any deviceswithin the geofenced area of the location, start time, and itemassociated with the on demand live auction. The local commerce servermay further manage messaging updates between clients and the artgallery. When the auction begins, the local commerce server may enableauction bids to be placed via clients' mobile devices.

In other example embodiments, rather than an on demand local auctionbeing initiated, the local commerce server may simply notify a merchantof the threshold interest, and the merchant may use this information totravel to a location within the geofenced area and set up an on demandlocal store that may be online or offline. An offline on demand localstore may be, for example, a booth at a temporary open air market, amobile food truck, a sidewalk sale, an informal auction in a publicplace, or other such in person commerce environments. In furtherembodiments, the local commerce server may automatically issue aconditional offer associated with the geofenced area, such as an offerto deliver products to the geofenced area if a certain number of theproducts are purchased within a certain time period. Other embodimentswill be apparent from the detailed descriptions provided herein.

For the purposes of this specification, the term “location” is used torefer to a geographic location, such as a longitude/latitudecombination, a street address, or a defined area. As described herein, alocation, location value, or location information may have associateduncertainty due to time delays and device movement, error inmeasurements, or other such sources of uncertainty. The term location isalso used within this specification in reference to a physical location,building, or area associated with a merchant, an event, or other similarphysical destination.

For the purposes of this specification and the associated claims, theterm “real-time” is used to refer to calculations or operationsperformed on the fly as events occur or input is received by theoperable system. However, the use of the term “real-time” is notintended to preclude operations that cause some latency between inputand response, so long as the latency is an unintended consequenceinduced by the performance characteristics of the machine.

For the purposes of this specification and the associated claims, theterm “geofence” is used to refer to various regions or boundaries ofinterest that include a geographic area within a distance or travel timeto a point of interest. However, a geofence need not be limited to anygeometric shape or an arbitrary boundary drawn on a map. Geofences canbe defined in terms of GPS coordinates (e.g., latitude and longitude)combined with a radius measured in meters or feet, for example.Alternatively, geofences can also be defined according to a series ofGPS coordinates defining a bounding box. In yet other examples, ageofence can be any geometric shape defined by a mathematical formulaand anchored by a GPS coordinate. Other methods of defining,maintaining, and using geofences can be used without limitation with thesystems and methods discussed herein. In certain examples, the geofencemay not be centered on a particular point or fixed coordinate, butrather allowed to float within a defined geographic area. In theseexamples, the defined float geography can be centered or otherwisedynamically tied to one or more points of interest (POIs), in order toprovide flexibility to a merchant for merchant thresholds. For example,a merchant may define a geofence as being any two block radius within a20 block area of a city, and the merchant may have interest thresholdsassociated with the floating two block radius geofence.

In other examples, the size or shape of a geofence may be dynamicallyconfigured to shift over the course of a day or some other time period.For example, between the hours of 10:00 AM and 4:00 PM, a geofence maybe set to a first area; between 4:00 PM and 6:00 PM, the geofence maydynamically adjust to a second area; and from 6:00 PM to 10:00 AM, thegeofence may be set to a null area to indicate that no threshold isassociated with that time period. In this example, the dynamic geofencemay change in size depending upon time of day. For example, a geofencemay grow smaller during commute times when travel is slower and mayexpand during times when travel is less congested and it is easier andquicker for a potential client to get to a commerce site.

For the purpose of this specification, the term “product” refers to anygoods, services, licenses, or other objects of a sales transaction thatmay be offered by a merchant to a client.

FIG. 1 is a block diagram depicting a system 100 for on demand localcommerce and local auctions, in accordance with one example embodiment.The example embodiment of FIG. 1 includes client device 110, localcommerce server 120, and merchant device 130. In general, local commerceserver 120 gathers client location information and interest informationfrom client device 110. Local commerce server 120 also gathers inputinformation from merchant device 130. This input information frommerchant device 130 is used to set thresholds that define when localcommerce actions and communications will be initiated by local commerceserver 120. Such actions are initiated when the location and interestinformation from client devices reach a threshold level that isdetermined from the merchant input information.

While the system 100 includes a single client device 110, a single localcommerce server 120, and a single merchant device 130, in variousembodiments of the system 100, any number of client devices such asclient device 110, local commerce servers such as local commerce server120, or merchant devices or servers such as merchant device 130 may bepart of a system. In certain embodiments, a single local commerce serverwill interact with hundreds or thousands of client devices and multiplemerchant devices. In other embodiments, the local commerce serverstructure described by local commerce server 120 and the structure ofmerchant device 130 may be integrated into a single device if the localcommerce server is being operated by the merchant. In still furtherembodiments, the system may use multiple local commerce servers. Thismay particularly occur if a local commerce server is dedicated to aparticular geographic area or a set of geographic areas. In suchembodiments, large areas may be covered by multiple local commerceservers with each local commerce server covering a particular subarea.

The communication relationships between client device 110, localcommerce server 120, and merchant device 130 may be established byregistration processes. Such processes may involve separate registrationfor a client and merchant. A client may register multiple client devicessuch as client device 110 with an account that is created to providelocal commerce information to the client via the client's devices.Similarly, a merchant that wishes to engage in local commerce activitieswith the assistance of a local commerce server such as local commerceserver 120 may register with local commerce server 120 and provideinformation about products, commerce times, and threshold requirementsrelated to local commerce activities that the merchant associated withmerchant device 130 will support. The registration process may alsoinvolve communication or downloading of applications, software elements,instruction sets, and the like to client device 110 and merchant device130 as part of their respective registration processes. This informationis received by client device 110 and merchant device 130 and may be usedas part of the modules operating on these respective devices toimplement local commerce as described herein. In certain embodiments,this information may be provided directly by local commerce server. Inother embodiments, this information may be provided by separate webportals, application servers, or other such network resources. Theseregistration processes may also be used to generate records at localcommerce server 120 identifying client devices and merchant devices,which will be used by the local commerce server 120 as described in moredetail further below.

Client device 110 includes client device location module 112, clientdevice profile module 114, and client local commerce application module116. Local commerce server 120 includes client location module 122,geofencing module 124, interest module 126, threshold module 128, andlocal commerce communication module 129. Merchant device 130 includesmerchant input module 132 and merchant local commerce application module134.

Client devices such as client device 110 are associated with aparticular client, a client account that is associated with multipleclient devices, or other such client device configurations. Clientdevice location module 112 may be one or more systems that are part ofclient device 110 for determining a location of client device 110 andsharing that location with networked computers such as local commerceserver 120. Client device location module 112 may include GPS receivers,processors for calculating a local position, network based locationservice systems, and other hardware and software systems that may beused to calculate or estimate a location of client device 110. Clientdevice location module 112 may periodically send a location update tolocal commerce server 120 as part of client device 110 system operation,or as part of an application operating on client device 110 such asclient local commerce application module 116. In various embodiments ofa client device, the systems for communicating client device locationsto a local commerce server may be structured in various different ways.

Client device profile module 114 accepts interest, preference, profile,or other such information provided by a user of the client device 110that may be used by local commerce server 120 and a merchant associatedwith merchant device 130 to identify local commerce opportunities thatmay interest a client of client device 110. Such information may begathered by a client interface presented on client device 110 as part ofoperation of an application that includes client device profile module114. This information may be gathered as part of a registration processwith a local commerce server 120 or may be communicated to localcommerce server 120 as part of system or application operation after aclient registration.

Client local commerce application module 116 operates an interface incommunication between a client of client device 110 and the localcommerce server 120. While client device location module 112 and clientdevice profile module 114 may operate on the background of client device110 in response to or following an initial client set up, client localcommerce application module 116 presents an active communicationinterface with the client of client device 110; thus, client localcommerce application module 116 may enable local commerce server 120 tocommunicate local commerce opportunities or offers to a client of clientdevice 110. For example, after the local commerce server 120 hasdetermined in conjunction with information from merchant device 130 thatan offer is available based on a location of client device 110, clientlocal commerce application module 116 may receive a communication fromlocal commerce server 120 regarding the offer or local commerceopportunity, and may present this information to a client of clientdevice 110 via an output device of client device 110. Client localcommerce application module 116 may also accept client inputs via aninput device of client device 110 to enable a client of client device110 to accept an offer or express further interest in a local commerceopportunity presented via client local commerce application module 116.

Local commerce server 120 operates to gather location information andinterest information from a client device 110. As discussed above, aninitial registration may be used to affiliate one or more client devicessuch as client device 110 with a client and local commerce server 120.Following the registration, a client device location module 112 ofclient device 110 may periodically communicate a location of clientdevice 110 to local commerce server 120. This information is received atlocal commerce server 120 by client location module 122. Client locationmodule 122 may receive location information from any number of clientdevices. Client location module 122 may associate this information withpreviously created accounts or identifiers. This information may then bepassed to geofencing module 124. Geofencing module 124 may receivebounding information from merchant input module 132 as well as theclient device location information from client location module 122.Geofencing module 124 may use these two sets of information to identifyclients that are within an area of interest that is associated with themerchant of merchant device 130. The bounding information from merchantinput module 132 may be a strictly defined area or may be weightedlocation preferences without a strictly defined boundary. For example,the bounding information may define a particular point or location witha weighted preference that decreases with distance from the identifiedpoint. In other embodiments, any other sort of location preferenceinformation may be provided as bounding information from merchant inputmodule 132. Additionally, in certain embodiments, merchant input module132 may provide multiple sets of bounding information to geofencingmodule 124, with each set of bounding information associated with aparticular product or offer. For example, this first set of boundinginformation may be associated with an offer to deliver food to aparticular location within 10 minutes. A second set of boundinginformation may be associated with an offer to deliver food to multiplelocations within the bounding area within 30 minutes. Thus, geofencingmodule 124 may receive not only bounding information associated with ageo-fenced area, but may also receive a product identifier or productinformation that is associated with the bounding information.

Interest module 126 receives information about client preferences fromclient device profile module 114. This information may initially bereceived upon the registration process where client device 110 isregistered with local commerce server 120. This information may also bereceived by a communication that occurs at any time from client deviceprofile module 114 sending interest information associated with a clientto interest module 126. Examples of interest information that may besent from a client device profile module 114 to interest module 126include food preferences, art preferences, musical preferences, or anypreference that may be associated with a product or service that may beprovided by a merchant associated with merchant device 130. Interestmodule 126 may take information about clients within an area of interestdetermined by geofencing module 124 and combine that with interestinformation from client device profile module 114 to generate aninterest level for a first product.

Threshold module 128 may then receive additional threshold informationfrom merchant input module 132, as well as geofencing information fromgeofencing module 124 and interest information from interest module 126.The additional threshold information from merchant input module 132 mayidentify an interest level at which the merchant wishes to provide orinitiate an offer to the client device 110. This interest level may bedefined by a particular number of client devices within the geo-fencedarea that have expressed interest in the product identified by merchantdevice 130. This interest level may also be a weighted value that isgenerated by any type of client interest information, geofencinginformation, and weighting factors provided by merchant device 130. Forexample, if interest information is received from multiple clients,certain clients may receive greater weight due to history informationassociated with previous purchases, profile information about particularclients and client devices indicating a greater likelihood of a positiveresponse to a merchant offer, or any other such information that maymake an offer more attractive or more feasible for a merchant.

As local commerce server 120 operates, new location information,interest information, and merchant inputs are received over time.Interest levels associated with particular geo-fenced areas and productsare compared with merchant provided thresholds as new information isreceived. If the threshold is not met, the system simply continuesgathering information and repeating the process of determining aninterest value and comparing that interest value with the thresholdinformation or levels provided by a merchant for a particular product.This process may occur simultaneously for many different products from asingle merchant, with each having associated boundary informationprovided by the merchant and interest thresholds provided by themerchant. Similarly, products from multiple different merchants may behandled by local commerce server 120 at the same time. If the interestthreshold for a product is met by the interest value calculated for thatproduct, local commerce server 120 will use local commerce communicationmodule 129 to initiate a local commerce message. Such a local commercemessage may be a message to merchant device 130 indicating that thethreshold for a particular product was met. Such a local commercemessage may also request authorization to take a local commerce actionsuch as communicating an offer from local commerce server 120 to clientdevice 110. In certain embodiments local commerce server 120 may haveprior authorization based on a communication from merchant device 130 toautomatically notify client device 110 that a local auction will takeplace at a particular time in response to the threshold being met. Localcommerce server 120 may also automatically make an offer or a contingentoffer for the product in a communication to client device 110 inresponse to a prior authorization from merchant device 130.

FIG. 2 illustrates a method for on demand local commerce, in accordancewith one example embodiment. The example embodiment of FIG. 2 may beimplemented with any local commerce server or system capable ofperforming the operations described below. For illustrative purposeshowever, the example embodiment of method 200 is described in thecontext of system 100.

Method 200 begins with operation 210 by receiving, at local commerceserver 120, location information associated with a first plurality ofclient devices that includes client device 110. In operation 220, thelocal commerce server 120 receives interest information associated withthe first plurality of client devices. This includes receipt of interestinformation from a client device 110. In operation 230, it is determinedthat the first plurality of client devices are within a first geographicarea during the first time period. This determination is done using thefirst location information associated with the first plurality of clientdevices.

Method 200 continues in operation 240 by calculating an interest levelfor a first product from the interest information associated with thefirst plurality of client devices including client device 110. Operation250 then involves identifying a threshold associated with the firstgeographic area and the first product. As described above, the thresholdmay be based both on bounding information and interest threshold valuesreceived from the merchant device 130. In certain embodiments, thisthreshold information may include both bounding information from themerchant device 130 that is used to determine or identify the firstgeographic area and client interest levels identified by merchant device130. All of this information may be received from merchant device 130along with information identifying the first product and associating thefirst product with the threshold and the first geographic area.

The method 200 then proceeds in operation 260 by determining that theinterest level for the first product exceeds the threshold. This may bea simple comparison of values. This may also be a complex operation thatcompares multiple geographic areas with different weighted interestvalues identified by a merchant in order to determine if an acceptablelevel of interest is present based on the first location information andthe interest information associated with the first plurality of clientdevices. Operation 270 then involves initiating a local commerce messageassociated with a first merchant in response to the determination thatthe interest level for the first product exceeds the threshold.

Though arranged serially in the example of FIG. 2, other examples mayreorder the operations, omit one or more operations, and/or execute twoor more operations in parallel using multiple processors or a singleprocessor organized as two or more virtual machines or sub-processors.Moreover, still other examples can implement the operations as one ormore specific interconnected hardware or integrated circuit modules withrelated control and data signals communicated between and through themodules. Thus, any process flow is applicable to software, firmware,hardware, and hybrid implementations.

FIG. 3 illustrates a method 300 for on demand local commerce, accordingto another example embodiment. The method 300 begins with merchant andclient registrations in operation 305. Any relevant information may begathered during the registration, including association of clients andmerchants with one or more devices, client interests, client preferencesfor contact details related to local commerce, initial merchant entry ofproduct details and associated thresholds, and any other such initialinformation. For example, a client may choose to receive email messages,short message service (SMS) messages, computerized voice messages,application alert messages, or any other such messages from a localcommerce server such as local commerce server 120. A client maysimilarly choose to receive particular types of these messages atcertain times and not at other times. Similar types of client optionsmay be selected for a merchant and the merchants associated devices. Forexample, a merchant may choose to receive messages on all of themerchant's associated devices during certain times and may choose toreceive messages on only one of the plurality of the merchant's devicesat other times. A merchant may elect to receive messages at certaintimes and to have automated local commerce actions taken without themerchant being contacted at other times.

During registration, a merchant may provide information for one or morelocal commerce products. This information may include sales options,such as a local offline auction option, a contingent multiple productoffer, response deadlines, and whether a local commerce server mayautomatically present an offer to clients or whether confirmation mustbe received from a merchant device before an offer is presented toclients.

After the initial registration, a system receives location informationfrom registered client devices in operation 310. How often thisinformation is received may be a client selected option that may be setduring registration and that may be modified as additionalcommunications are received from a client device. A client may elect tohave location information sent periodically, when a client device iswithin a certain geographic area, or only when a particular option isselected via a client interface of a client device location module orclient local commerce application module operating on a client device.

Operation 320 then involves geofencing using the received locationinformation and any bounding information received from a merchantdevice. The bounding information may be received either as part of themerchant registration or as part of a subsequent update from themerchant related to local commerce operations for a particular productor set of products. In various embodiments, a single geofencingoperation may be associated with multiple merchant local commerceproducts and offers, or a geofencing operation may be associated with asingle merchant local commerce product and offer. The geofencing ofoperation 320 may use strict boundaries provided by a merchant, or mayinvolve a boundary that is generated using merchant criteria and thelocation information from client devices received in operation 310.Additional information related to geofencing processes are describedbelow.

In operation 330, an interest level is calculated for a particular localcommerce product. The interest level may be performed using onlyinterest information for clients with an associated client device thathas been within the geographic area identified by the geofencingoperation within a predetermined time period. In other exampleembodiments, a per client interest level in the local commerce productmay be identified for all system clients, and the geofencing informationmay be used to filter clients not relevant to a particular localcommerce offer.

In operation 340, an interest threshold is determined. This may simplybe a value provided by a merchant, or may be a calculated result of aformula with dynamic inputs such as the weather, the time of day, thetime of year, recent merchant sales, client use of the system, or othersuch dynamic inputs.

In operation 350, the system determines if the calculated interest levelmeets or exceeds the interest threshold. Various embodiments may be setsuch that a calculated interest level may exceed or be equal to thethreshold in order to trigger a local commerce action.

For example, a merchant may wish to offer an on demand auction ofhandmade furniture, including a handmade antique chair, at an outdoormarket. The merchant may upload a picture and description of the chairto a local commerce server as part of a registration, and the merchantmay select interest weighting values and an offer period of 10 AM to 2PM on a particular day of the outdoor market. A registration process fora client or a local commerce application on a client's device may prompta client to select an interest level for a number of categories, such asantique furniture, on a scale of one to ten. This information may begathered and stored at a local commerce computer system. The localcommerce system may additionally gather client profile information fromany number of other sources. For example, the system may store a recordof furniture purchases for a client. The local commerce system maygenerate a data driven interest value using sources, such as thepurchase history, to generate a value that is also on a scale of one toten. The client interest input and the data driven value may be added tocreate an individual client interest score, where (client interestinput)+(data driven interest)=(individual client interest score). Theindividual client interest scores may then be weighted by proximity tothe auction location. For example, a location information communicationindicating that a device was at an auction location within the last 5minutes may be weighted at 100% and may then linearly scale down so thata location 2000 feet away will be scaled to zero. Thus, a client device1000 feet away will have the client's interest score cut in half, andclient devices more than 2000 feet away will be outside the geofencingboundary. Thus:

-   -   (1) if geofence boundary distance to auction site>device        distance to auction site, then: [(geofence boundary−device        distance from auction site)/(boundary distance)]*[(client        interest input)+(data driven interest)]=(weighted individual        client interest value)        -   and        -   if geofence boundary distance to auction site<device            distance to auction site, then: weighted individual client            interest value=0.            The sum of all the weighted individual client interest            values may be the interest level calculated by the system            for the furniture auction. For example, a merchant may set            an interest level threshold of 200, such that 11 client            device measurements at the auction location, where all 11            clients each have at or near the maximum interest score of            20, will trigger an auction (i.e. 11 device measurements            each with an interest score of 20 will provide an interest            level of 220 which is above the threshold of 200.)

In other embodiments, other weighting factors may be used. For example,a multiplier may be used as the day gets later and the end of the marketapproaches, with a trigger for the merchant to indicate that the chairhas been sold. Alternatively, the interest threshold may decrease overtime, such that a lower interest level will be required later in theday. This would, for example, support an auction near the end of the dayif there is interest in a product and a storefront or booth price is notmet during the day.

If, in operation 350, the interest level does not exceed the threshold,then in operation 360 the process repeats and returns to operation 310.Operation 360 may involve record storage and creation of historical datathat may be used as feedback for any dynamic aspects of geofencing orinterest level calculation. As the process repeats, any dynamic valuessuch as time or device location may be updated, and the process mayrepeat. In certain embodiments, a local commerce product may becanceled. For example, in the auction product described above, if achair sells at a storefront of the open market, the merchant may send amessage to the local commerce server that the on demand auction for thechair is no longer available, and the local commerce server will ceasechecking the interest level and the threshold for the chair.

If, in operation 350, the interest level does exceed the threshold, thenthe process proceeds with operation 370, and the initiation of a localcommerce communication. The particular local commerce communication thatis initiated will depend on merchant selections for a particular localcommerce product. If a merchant has enabled or authorized a localcommerce server to automatically create an offer, then the localcommerce communication that is part of operation 370 may be sentdirectly to a plurality of client devices. This communication may besent only to client devices that have been within the geo-fenced area asdetermined by operation 320, to any device that has been within or nearthe geofencing area within the predetermined time, or sent to all clientdevices that have elected to receive such communications. Systems thatsend such local commerce communications to all authorized client devicesmay be used to incentivize clients that are outside of the geofencingarea to participate even though the interest of those clients was notused in calculation of the interest level.

In certain local commerce offerings, a merchant may receive the localcommerce communication of operation 370 and may send a confirmationmessage to the local commerce server verifying that a local commerceoperation will proceed. If the local commerce operation is eitherconfirmed by the merchant or performed automatically, the system willproceed with the operation as defined by the merchant. This may includea local live auction as illustrated by operation 372. This mayalternatively include a contingent offer as illustrated by operation374. Any other type of offer or combination of such offers allowable bythe system and selected by a merchant can result from the determinationthat the interest level exceeds the threshold.

As part of any local commerce operations that may be initiated by adetermination that an interest value has exceeded a threshold value, asystem may continue to gather and update location information,geofencing, and interest information in operation 371, and use thisinformation to initiate further local commerce communications inoperation 370. For example, if additional client devices enter ageofenced area after a local commerce auction has been initiated, butbefore conclusion of the auction, the client devices may be sent localcommerce communications informing the client devices of the localauctions.

In one embodiment, if a sufficient number of client devices leave ageofenced area after the local commerce action has been initiated, thenas part of operation 371, the local commerce action may be delayed,canceled, or moved, with an associated communication sent following thischange in operation 370. In certain embodiments, a system may includemultiple thresholds. For example, a first threshold may result in aninitial local commerce communication indicating that a basic interestthreshold has been met, and a local commerce event will be initiated ifa second interest threshold greater than the basic interest threshold ismet, then a local commerce action will be initiated. Such an initiallocal commerce action may be a communication requesting feedback. Thefeedback may then be used in updating the interest value. If the secondinterest level is not met, then the local commerce action will not beinitiated. If the second interest level is met, but then the interestvalue drops below the basic interest threshold, then the event may becanceled or moved. In certain embodiments, a cancelation warning may besent when the interest value drops below the second threshold, and thecancelation message sent after the interest value drops below the basicthreshold.

Additionally, as described above, geofencing operations may continue aspart of operation 371. If, after an initial local commerce communicationin operation 370, a shift is seen in the geographic area associated withthe interest as part of operation 371, this may initiate a subsequentlocal commerce communication operation 370 that communicates a shift inthe geographic area associated with the local commerce event or action.Such processes as part of operation 371 may involve multiple repeatedprocesses of any combination of operations that are part of method 300.In certain embodiments, these repetitions of geofencing, locationinformation reception, and threshold calculation may occur continuously,periodically, or in response to a system trigger. In certainembodiments, certain repeated operations may occur periodically, andothers may be triggered as part of the same overall system. Duringrepetition of these operations as part of operation 371, any localcommerce operations may continue as data analysis and geofencingdeterminations continue as part of operation 371.

If optional operation 372 is part of the local commerce offer with alocal live auction, a local commerce communication to client devices mayprovide product details such as a product picture, an auction startprice, a price raise increment, auction format information including bidtimings, or any other such auction details. As part of such an auction,when the auction starts, the local commerce server may receive clientcommunications including auction bids as part of operation 378. When theauction closes, client devices may be sent offer terminationcommunications in operation 376. If a successful bid is received duringoperation 373, the local commerce server may proceed to paymentprocessing in operation 380. Such a payment processing operation may beautomatically performed using payment details that were previouslyprovided by a client during the registration process, may involve arequest and response with a client for payment information before theprocess closes, or may involve any other such payment process. Incertain embodiments, the payment process of operation 380 may beperformed by the local commerce server. In other embodiments, a separatepayment processing device may be used to perform operation 380. Incertain embodiments, if a successful bid is received but payment is notsuccessfully authorized within a certain time, the process may repeat atoperation 310 (not illustrated in the flow.)

If, alternatively, the local commerce action is not an auction but isinstead a contingent offer, then the method 300 will proceed withoperation 374. An example of such a contingent offer may be an offer todeliver furniture to a particular area if a sufficient number offurniture articles are purchased or if a sufficient dollar value offurniture articles are purchased as part of the offer within aparticular time period. If the contingency is not met, then an offertermination communication may be sent to relevant client devices thatreceived the offer as part of operation 376. Offers may be received fromclient devices as part of client communications in operation 378. Justas with the auction processes, if sufficient offers are received and thelocal commerce action is successful, payment processing may be performedin operation 380 prior to final confirmation that the contingent offerhas been accepted. For example, if a contingent offer requires a sale of$5000 worth of furniture for sale and delivery to a particular locationand $6000 worth of furniture is accepted in client communications aspart of operation 378, but payment is only successfully processed for$4000 worth of the furniture in operation 380, then the contingent offerwill fail, and the process may repeat at operation 310. If thecontingent offer is met including successful payment processing orcompletion of any other merchant requirements, then the processcompletes and communications may be sent to purchasing client devicesand merchants with verifying details associated with the sale of thelocal commerce product.

FIG. 4 illustrates a system that may be used to enable on demand localcommerce in certain example embodiments. In an example, system 400 caninclude client devices 410A-410N (collectively referred to as eitherclient device 410 or client devices 410 depending upon context) and alocal commerce system 420. In certain embodiments, client devices410A-410N may function similarly to client device 110 of system 100discussed above, and local commerce system 420 may function in a mannersimilar to local commerce server 120. In various embodiments, localcommerce server 420 may or may not integrate merchant devicefunctionality similar to merchant device 130. In an example, the clientdevices 410A-410N can connect to the local commerce system 420 viamobile devices 415A-415N (collectively referred to as mobile device415). Client devices 410A-410N can also connect to the local commercesystem 420 via client devices 440A-440N (collectively referred to asclient device 440 or client devices 440). In certain examples, clientdevices 410 can receive communications, on mobile devices 415 or clientdevices 440, from the local commerce system 420 transmitted over network405, but the client devices 410 may not otherwise make any sort ofdirect connection with the local commerce system 420.

In an example, the client devices 410 can configure an account on thelocal commerce system 420. The account can be accessed by a client, suchas client device 410A, using mobile device 415A or client device 440A,if client device 410A meets the specified access criteria or rules. Inan example, the access rules can include client identification and/ormobile device identification. A client account on the local commercesystem 420 can allow the client to define specific products of interestor provide other client data that can be used by the local commercesystem 420. In some examples, the local commerce system 420 can monitorclient behavior and create geofences based on past and predicted clientbehaviors in response to merchant criteria. This may enable merchants toprovide abstractly defined geofencing parameters to identify thresholdinterest levels where clients, using client devices 410, opt-in toreceive local commerce communications. Such abstractly definedgeofencing parameters may include geofences created with interest levelsbased on client locations and interests, but with a search area forgeneration of the geofences that is much larger than the createdgeofence. For example, an entire state may be a search area coveringmillions of square miles, with geofences created when client devices arewithin an area that is on the order of a single city block or within asingle store. For example, an electronics store may use on demand localcommerce to offer promotional prices to client devices in a particulargeographic area at a particular time. Such a local commerce system mayuse dynamic geofences to target a geographic area that is likely toinclude a segment of client devices 410 that meet express interest in aparticular type of local commerce product.

FIG. 5 is a block diagram illustrating an environment 500 for operatinga mobile device 415, according to an example embodiment. As mentionedabove, mobile device 415 may operate as a client device 110 in certainembodiments. The environment 500 is an example environment within whichmethods for using on demand local commerce can be implemented. Theenvironment 500 can include a mobile device 415, a communicationconnection 510, a network 520, local commerce servers 530, acommunication satellite 570, a merchant server 580, and a database 590.Merchant server 580 may, in certain embodiments, be similar to merchantdevice 130 of system 100. The local commerce servers 530 can optionallyinclude location based service (LBS) application 540, locationdetermination application 550, communication application 560, andgeofence application 565. The database 590 can optionally includedemographic data 595, user profiles 594, and/or location history 596.The mobile device 415 represents one example device that can be utilizedby a client to receive local commerce communications.

The mobile device 415 may be any of a variety of types of devices (forexample, a cellular telephone, a personal digital assistant (PDA), aPersonal Navigation Device (PND), a handheld computer, a tabletcomputer, a notebook computer, or other type of movable device). Themobile device 415 may interface via a connection 510 with acommunication network 520. Depending on the form of the mobile device415, any of a variety of types of connections 510 and communicationnetworks 520 may be used.

For example, the connection 510 may be Code Division Multiple Access(CDMA) connection, a Global System for Mobile communications (GSM)connection, or other type of cellular connection. Such connection 510may implement any of a variety of types of data transfer technology,such as Single Carrier Radio Transmission Technology (1xRTT),Evolution-Data Optimized (EVDO) technology, General Packet Radio Service(GPRS) technology, Enhanced Data rates for GSM Evolution (EDGE)technology, or other data transfer technology (e.g., fourth generationwireless, 7G networks). When such technology is employed, thecommunication network 520 may include a cellular network that has aplurality of cell sites of overlapping geographic coverage,interconnected by cellular telephone exchanges. These cellular telephoneexchanges may be coupled to a network backbone (for example, the publicswitched telephone network (PSTN), a packet-switched data network, orother types of networks).

In another example, the connection 510 may be a Wi-Fi or IEEE 802.11xtype connection, a Worldwide Interoperability for Microwave Access(WiMAX) connection, or another type of wireless data connection. In suchan embodiment, the communication network 520 may include one or morewireless access points coupled to a local area network (LAN), a widearea network (WAN), the Internet, or other packet-switched data network.

In yet another example, the connection 510 may be a wired connection,for example an Ethernet link, and the communication network may be aLAN, a WAN, the Internet, or other packet-switched data network.Accordingly, a variety of different configurations are expresslycontemplated.

The above communication technologies may be used both for local commercecommunications and also to assist in location determination of mobiledevice 415 in order to generate location information with networkassisted location based services. This location information mayadditionally use sensor information and satellite signals in thegeneration of location information, and the location information maythen be communicated from mobile device 415 to local commerce servers530.

A plurality of local commerce servers 530 may be coupled via interfacesto the communication network 520, for example, via wired or wirelessinterfaces. These local commerce servers 530 may be configured toprovide various types of services to the mobile device 415. For example,one or more local commerce servers 530 may execute LBS applications 540,which interoperate with software executing on the mobile device 415, toprovide LBSs to a client. LBSs can use knowledge of the device'slocation, and/or the location of other devices, to providelocation-specific information, recommendations, notifications,interactive capabilities, and/or other functionality to a client. Forexample, an LBS application 540 can provide location data to a localcommerce server 120, which can then be used to provide location-awarecommunications from the local commerce server 120, where local commerceservers 530 can be operating with the local commerce server 120.Knowledge of the device's location, and/or the location of otherdevices, may be obtained through interoperation of the mobile device 415with a location determination application 550 executing on one or moreof the local commerce servers 530. Location information may also beprovided by the mobile device 415, without use of a locationdetermination application, such as application 550. In certain examples,the mobile device 415 may have some limited location determinationcapabilities that are augmented by the location determinationapplication 550. In some examples, the local commerce servers 530 canalso include communication application 560 for providing local commercecommunications with client devices and merchant devices. Thesecommunications may include notifications of offers, bid communicationsfor on demand local auctions, payment communications, system settingcommunications, or any other such communications. In certain examples,location data can be used by the communication application 560 alongwith geofencing information and additional location information providedby the location determination application 550. In some examples, thelocation data provided by the location determination application 550 caninclude merchant information (e.g., identification of a retail location)that is associated with on demand local auctions or other local commerceactions or offers. In certain examples, the location determinationapplication 550 can receive signals via the network 520 to furtheridentify a location. For example, a merchant may broadcast a specificIEEE 802.11 service set identifier (SSID) that can be interpreted by thelocation determination application 550 to identify a particular retaillocation. In another example, the merchant may broadcast anidentification signal via radio-frequency identification (RFID),near-field communication (NFC), or a similar protocol that can be usedby the location determination application 550. In addition to examplesusing these various mechanisms to identify a particular location, thesemechanisms (e.g., SSIDs, RFIDs, NFC, and so forth) can be used assecondary authentication factors, which are discussed in more detailbelow.

In certain examples, the geofence application 565 can leverage the LBSapplication 540 or the location determination application 550 to assistin generating and/or updating geofences based on guidelines provided bya merchant and associated with a particular local commerce event.Additional information such as current or historical user data andstatistics may also be used by the geofencing application 565 to assistin generating or updating geofences. For example, a merchant may provideproduct information and geofencing guideline information to a localcommerce server. The local commerce server may use this informationalong with historical location data seen by the system to generate ageofence. This geofence may then be used with location data receivedfrom client devices to calculate interest levels and compare theinterest levels with a threshold determined using the merchantguidelines.

FIG. 6 is a block diagram illustrating the mobile device 415, accordingto an example embodiment. The mobile device 415 may include a processor610. The processor 610 may be any of a variety of different types ofcommercially available processors suitable for mobile devices (forexample, an XScale architecture microprocessor, a Microprocessor withoutInterlocked Pipeline Stages (MIPS) architecture processor, or anothertype of processor). A memory 620, such as a Random Access Memory (RAM),a Flash memory, or other type of memory, is typically accessible to theprocessor. The memory 620 may be adapted to store an operating system(OS) 630, as well as application programs 640, such as a mobile locationenabled application that may provide LBSs to a client. The processor 610may be coupled, either directly or via appropriate intermediaryhardware, to a display 650 and to one or more input/output (I/O) devices660, such as a keypad, a touch panel sensor, a microphone, and the like.Similarly, in some embodiments, the processor 610 may be coupled to atransceiver 670 that interfaces with an antenna 690. The transceiver 670may be configured to both transmit and receive cellular network signals,wireless data signals, or other types of signals via the antenna 690,depending on the nature of the mobile device 415. In this manner, theconnection 510 with the communication network 520 may be established.Further, in some configurations, a GPS receiver 680 may also make use ofthe antenna 690 to receive GPS signals.

FIG. 7 is a block diagram illustrating a network-based system 700 forusing on demand local commerce, according to an example embodiment. Theblock diagram depicts a network-based system 700 (in the exemplary formof a client-server system), within which an example embodiment can bedeployed. A networked system 702 is shown, in the example form of anetwork-based local commerce system, that provides server-sidefunctionality, via a network 704 (e.g., the Internet or WAN) to one ormore client machines 710, 712. FIG. 7 illustrates, for example, a webclient 706 (e.g., a browser, such as the Internet Explorer browserdeveloped by Microsoft Corporation of Redmond, Washington State) and aprogrammatic client 708 (e.g., an eBay smart phone application fromeBay, Inc. of San Jose Calif.) executing on respective client machines710 and 712. In an example, the client machines 710 and 712 can be inthe form of a mobile device, such as mobile device 415.

An Application Programming Interface (API) server 714 and a web server716 are coupled to, and provide programmatic and web interfacesrespectively to, one or more application servers 718. The applicationservers 718 host one or more communication modules 720 (in certainexamples, these can also include commerce modules, advertising modules,and marketplace modules that may be used for on demand local commerce toname a few), payment modules 722, and geofencing modules 732. Theapplication servers 718 are, in turn, shown to be coupled to one or moredatabase servers 724 that facilitate access to one or more databases726. In some examples, the application server 718 can access thedatabases 726 directly without the need for a database server 724.

The communication modules 720 may provide a number of communicationfunctions and services to clients and merchants who access the networkedsystem 702. The payment modules 722 may likewise provide a number ofpayment services and functions to clients and merchants. The paymentmodules 722 may allow clients to accumulate value (e.g., in a commercialcurrency, such as the U.S. dollar, or a proprietary currency, such as“points”) in accounts, and then later to redeem the accumulated valuefor products (e.g., goods or services) that are advertised or madeavailable via on demand local commerce from merchants. The paymentmodules 722 can also be configured to facilitate payment processingbased on geofence detection and work in conjunction with the geofencingmodules 732 as described above in the example embodiment of method 300.The geofencing modules 732 may provide generation and updating of ondemand local commerce, among other things. While the communicationmodules 720, payment modules 722, and geofencing modules 732 are shownin FIG. 7 to all form part of the networked system 702, it will beappreciated that, in alternative embodiments, the payment modules 722may form part of a payment service that is separate and distinct fromthe networked system 702.

Further, while the system 700 shown in FIG. 7 employs client-serverarchitecture, the present invention is of course not limited to such anarchitecture, and could equally well find application in otherstructures such as a distributed, or peer-to-peer, architecture system,for example.

The web client 706 accesses the various communication modules 720,payment modules 722, and geofencing modules 732 via the web interfacesupported by the web server 716. Similarly, the programmatic client 708accesses the various services and functions provided by thecommunication modules 720, payment modules 722, and geofencing modules732 via the programmatic interface provided by the API server 714. Theprogrammatic client 708 may, for example, be a smart phone applicationthat enables clients to pass location information to a local commerceserver, provide interest information to a local commerce server, andsend and receive bid and offer communications as part of on demand localcommerce. In certain embodiments, a programmatic client 708 may be usedto submit bids in an on demand local commerce auction environment wherean auctioneer and a physical product are at the same location as theclient machine 712. A verbal auction offer may be made during the ondemand local auction, and a user may respond by submitting an increasedbid using the programmatic client 708 operating on the client machine712. This may involve a text input via a keyboard or touchscreeninterface. This may also involve movement of client machine 712, such asraising client machine 712 like an auction paddle. In certainembodiments, the programmatic client may receive a networkedcommunication about a current auction level, and an accelerometer ormotion sensor within client machine 712 may detected a raising motionthat is accepted as an input to submit an offer increasing the bid by aminimum bid amount. This input may be communicated to a local commerceserver and relayed to a merchant device. The merchant device will thencommunicate the updated bid level to other client devices involved inthe auction.

FIG. 7 also illustrates a third party application 728, executing on athird party server machine 740, as having programmatic access to thenetworked system 702 via the programmatic interface provided by the APIserver 714. For example, the third party application 728 may, utilizinginformation retrieved from the networked system 702, support one or morefeatures or functions on a website hosted by the third party. The thirdparty website may, for example, provide one or more promotional,marketplace, or payment functions that are supported by the relevantapplications of the networked system 702. Additionally, the third partywebsite may provide merchants with access to the geofencing modules 732for on demand local commerce processes.

FIG. 8 is a block diagram illustrating geofencing modules 732, accordingto an example embodiment. In this example, the geofencing modules 732can include a rules engine 805, a communication module 810, a generationmodule 820, a data collection module 830, and a location module 840. Inan example, the geofencing modules 732 can access database 726 to storeand/or retrieve generation rules, client profile data, location data,and demographic data, as well as other information, to enable dynamicgeofencing.

In an example, the rules engine 805 can be configured to manage andevaluate rules controlling geofence generation and updating. Rules canbe provided by a merchant on a per product basis, per event basis, perproduct category basis, or on any other such basis. One of the “rules”can define the type of statistical analysis as well as the targetdemographic or subset of system clients to be used in generating orupdating a geofence. For example, a geofence rule may correlate thegeofence radius to population density of the target geographical area.In some example local commerce actions, a merchant may want to avoidhaving too many or too few attendees at a local commerce auction inorder to provide an ideal client environment. In this example, the lowerthe population density, the larger the radius of the resulting geofence.Accordingly, for a franchisee with locations in different geographicareas, such a rule can allow for locations in low density areas andlocations in high density areas to still attempt to provide astandardized local commerce experience.

In an example, the communication module 810 can be configured to managecommunications between the geofencing modules 732 and a client, wherethe client is communicating via the mobile device 415 or the clientdevice 110. The communication module 810 can also be configured tomanage communications between the geofencing modules 732 and a merchant.For example, the geofencing module may determine which client devicesout of all client devices in a system will receive certain on demandlocal commerce communications based on the location information for adevice as associated with a geofence generated by geofencing modules732.

In an example, the generation module 820 is configured to generate andupdate geofences according to information provided by modules, such asthe data collection module 830, the location module 840, and the rulesengine 805.

In an example, the location module 840 is configured to receive locationdata from a mobile device, such as mobile device 415, and determine fromthe location data a current physical location, which may includereference to landmarks or other sites of interest. In some examples, thelocation module 840 can receive GPS-type coordinates (e.g., longitudeand latitude), which can be used to establish a current locationassociated with a mobile device (and, thus, a client of the mobiledevice). Using the longitude and latitude coordinates, the locationmodule 840 can determine if the current location is within a geofence,for example. In another example, some merchants may broadcast specificwireless network signals that can be received by a mobile device, suchas mobile device 415. Once received, the mobile device 415 can includeprogramming or circuitry to translate the signal into a specificlocation, or the mobile device 415 can simply retransmit the uniquesignal to the location module 840. In an example, a merchant locationcan transmit a unique SSID, which the location module 840 can beprogrammed to interpret as identifying a specific merchant location. Inanother example, the merchant may broadcast a unique SSID within all ofits locations and the location module 840 can be programmed to use acombination of the unique SSID and other location data (e.g., GPScoordinates or cell tower locations) to identify a specific location

FIG. 9 is a diagram illustrating geofence updating via statisticalanalysis, according to an example embodiment. The map display 900includes a number of geofences (910, 920, and 930) and highlightedlocations (A-J). In this example, three geofences are illustratedincluding two dynamic geofences 910 (910A, 910B) and 920 (620A, 920B)and one static geofence 930. All of the illustrated geofences can beused to determine an interest level associated with a product, and totarget communications to client devices within a limited geographic areaif the interest level associated with the product in the geofenced areaexceeds a threshold. Further, even geofence 930, which is illustrated asa static or unchanging, can be updated to change its size or shape atsome future point in time.

In an example, geofence 910A can represent an initial state of geofence910 generated around location C. Location C may be, for example, apotential site of an on demand local commerce auction for a merchant'sproduct. Geofence 910 represents a simple circular geofence centered onlocation C. In this example, geofence 910 can include a geofenceparameter defining the radius of the dynamic geofence. In an example,the geofence parameter for geofence 910 can be based on a merchantselection, traffic information that may influence the ability of clientsto travel to location C, target demographic information, or other suchinformation. In this example, the geofence 910 can shift between a firstgeofence parameter value resulting in geofence 910A and a secondgeofence parameter value resulting in geofence 910B due to shifts in thetime of day, travel conditions, weather, merchant direct input settings,or any other such geofence parameter.

In another example, geofence 920 represents a more complex geofence laidout to cover a particular geographic area, which may correlate tocertain traffic patterns, local retail locations, or client demographicdata, among other things. Geofence 920 can be defined by a series ofcoordinates (latitude/longitude pairs), city block designations, orstreet intersections, among other things. Geofence 920 also illustratesthe potential for a geofence to shift in shape due to changes in relateddemographics or other statistical data driving the particular shape. Forexample, an advertiser may want to avoid areas of a city that includecompeting locations, and such locations may change over time. In anexample, a food truck operator may request that the local commerceserver 120 run an on demand local commerce offer within the operatingarea for the food truck for a particular time frame. Geofence 920 canillustrate two different operating areas 920A and 920B, which mayrepresent areas targeted on different days of the week or a shift inareas based on changes in competitor locations. While geofence areas920A and 920B overlap, as illustrated in FIG. 9, there is no requirementfor overlap between iterations of a dynamic geofence.

Thus, an additional example embodiment that conforms with theimplementations described above comprises a method including receiving,at a local commerce server computer using one or more processors, firstlocation information associated with a first plurality of clientdevices; receiving, at the local commerce server computer, interestinformation associated with the first plurality of client devices;determining that the first plurality of client devices are within afirst geographic area during a first time period using the firstlocation information associated with the first plurality of clientdevices; calculating an interest level for a first product from theinterest information associated with the first plurality of clientdevices; identifying a threshold associated with the first geographicarea and the first product; determining that the interest level for thefirst product exceeds the threshold; and initiating a local commercemessage associated with a first merchant in response to the determiningthat the interest level for the first product exceeds the threshold.

Further implementations of such an example embodiment may operate wherethe local commerce message is an on demand live auction notification.Further implementations of such an example embodiment may operate byreceiving a first auction input identifying the first geographic areafrom a first merchant computer associated with the first merchant;receiving a second auction input identifying the first product; andreceiving a third auction input setting the threshold.

Further implementations of such an example embodiment may operate bycommunicating an auction notification message to the first plurality ofclient devices, wherein the auction notification message comprisesproduct information associated with the first products and an auctionstart time.

Further implementations of such an example embodiment may operate wherethe auction notification message further comprises coordinates for anauction location that is within the first geographic area.

Further implementations of such an example embodiment may operate byreceiving an auction bid communication from a first client device afterthe auction start time; communicating a first auction update to thefirst plurality of client devices in response to receipt of the auctionbid communication; and communicating a seller auction update to anauction device associated with the first merchant.

Further implementations of such an example embodiment may operate wherethe local commerce message comprises a conditional sale offer associatedwith the first product. Further implementations of such an exampleembodiment may operate where the conditional sale offer comprises adelivery location within the geographic area, an acceptance time window,a delivery time window, and a threshold acceptance quantity.

Further implementations of such an example embodiment may operate byreceiving a first acceptance communication from a first client device ofthe first plurality of client devices and communicating a thresholdacceptance update to the first plurality of client devices.

Further implementations of such an example embodiment may operate byreceiving a second acceptance communication from a second client deviceof the first plurality of client devices; determining that the thresholdacceptance quantity has been met; automatically performing a firstpayment process associated with the first acceptance communication;automatically performing a second payment process associated with thesecond acceptance communication; determining that payment has beenreceived for the threshold acceptance quantity of the first product; andautomatically communicating a purchase confirmation message to the firstdevice and the second device in response to the determining that paymenthas been received for the threshold acceptance quantity of the firstproduct.

Further implementations of such an example embodiment may operate wherethe conditional sale offer further comprises a maximum acceptance value.

Further implementations of such an example embodiment may operate byreceiving a first acceptance communication from a first client device;determining that the maximum acceptance value has been met; andcommunicating an offer termination message to the first plurality ofclient devices in response to the determination that the maximumacceptance value has been met.

Further implementations of such an example embodiment may operate byreceiving second location information associated with a second pluralityof client devices and at least a portion of the first plurality ofclient devices, wherein the first location information is receivedduring the first time period, and wherein the second locationinformation is received during a second time period that is later thanthe first time period; receiving, at the local commerce server computer,interest information associated with the second plurality of clientdevices; determining that the second plurality of client devices and theat least a portion of the first plurality of client devices are withinthe first geographic area during the second time period using the secondlocation information; calculating a second interest level for the firstproduct from the interest information associated with the secondplurality of client devices and the interest information associated withthe at least a portion of the first plurality of client devices; andinitiating a local commerce update message based on the second interestlevel.

Further implementations of such an example embodiment may operate wherethe local commerce message comprises an offline market recommendation,and wherein the offline market recommendation comprises a recommendedquantity associated with the first product; and wherein the localcommerce update message comprises an updated recommendation quantitybased on the second interest level.

An additional example embodiment in accordance with the innovationsdescribed herein may be a local commerce server system made up of aclient interest profile module that receives interest informationassociated with a first plurality of clients and stores the interestinformation in a memory of the local commerce server system. Such alocal commerce server system may additionally include a locationdetermination module operating with one or more processors that receivesfirst location information associated with a first plurality of clientdevices, wherein each device of the first plurality of client devices isassociated with a client of the first plurality of clients. Such a localcommerce server system may additionally include a geofencing moduleoperating with the one or more processors that determines that the firstplurality of client devices are within a first geographic area using thefirst location information associated with the first plurality of clientdevices. Such a local commerce server system may additionally include alocal commerce module operating with the one or more processors thatcalculates an interest level for a first product from the interestinformation associated with the first plurality of client devices,identifies a threshold associated with the first geographic area and thefirst product, and determines that the interest level for the firstproduct exceeds the threshold. Such a local commerce server system mayadditionally include a communication module coupled to the memory andthe one or more processors that initiates a local commerce messageassociated with a first merchant in response to the determining that theinterest level for the first product exceeds the threshold.

Additional implementations of such a local commerce server may furtherinclude a merchant local commerce application module that stores productinformation comprising product details for a plurality of products,bounding information associated with each product of the plurality ofproducts, and threshold information associated with each product of theplurality of products, where the merchant local commerce application isconfigured to provide the product information to the local commercemodule via a merchant input module of the local commerce server system.

An additional example embodiment may be a non-transitory computerreadable medium comprising computer readable instructions that, whenexecuted by one or more processors, cause a device to: receive, at thedevice, first location information associated with a first plurality ofclient devices; receive interest information associated with the firstplurality of client devices; determine that the first plurality ofclient devices are within a first geographic area during a first timeperiod using the first location information associated with the firstplurality of client devices; calculate an interest level for a firstproduct from the interest information associated with the firstplurality of client devices; identify a threshold associated with thefirst geographic area and the first product; determine that the interestlevel for the first product exceeds the threshold; and initiate a localcommerce message associated with a first merchant in response to thedetermining that the interest level for the first product exceeds thethreshold.

While these and other example embodiments are specifically describedherein, it will be apparent to a person of ordinary skill in the artthat additional embodiments are possible within the scope of theinnovations that are described herein and illustrated by the exampleembodiments.

Certain embodiments are described herein as including logic or a numberof components, modules, or mechanisms. Modules may constitute eithersoftware modules (e.g., code embodied on a machine-readable medium or ina transmission signal) or hardware modules. A hardware module is atangible unit capable of performing certain operations and may beconfigured or arranged in a certain manner. In example embodiments, oneor more computer systems (e.g., a standalone, client, or server computersystem) or one or more hardware modules of a computer system (e.g., aprocessor or a group of processors) may be configured by software (e.g.,an application or application portion) as a hardware module thatoperates to perform certain operations as described herein.

In various embodiments, a hardware module may be implementedmechanically or electronically. For example, a hardware module maycomprise dedicated circuitry or logic that is permanently configured(e.g., as a special-purpose processor, such as a field programmable gatearray (FPGA) or an application-specific integrated circuit (ASIC)) toperform certain operations. A hardware module may also compriseprogrammable logic or circuitry (e.g., as encompassed within ageneral-purpose processor or other programmable processor) that istemporarily configured by software to perform certain operations. Itwill be appreciated that the decision to implement a hardware modulemechanically, in dedicated and permanently configured circuitry, or intemporarily configured circuitry (e.g., configured by software) may bedriven by cost and time considerations.

Accordingly, the term “hardware module” should be understood toencompass a tangible entity, be that an entity that is physicallyconstructed, permanently configured (e.g., hardwired) or temporarilyconfigured (e.g., programmed) to operate in a certain manner and/or toperform certain operations described herein. Considering embodiments inwhich hardware modules are temporarily configured (e.g., programmed),each of the hardware modules need not be configured or instantiated atany one instance in time. For example, where the hardware modulescomprise a general-purpose processor configured using software, thegeneral-purpose processor may be configured as respective differenthardware modules at different times. Software may accordingly configurea processor, for example, to constitute a particular hardware module atone instance of time and to constitute a different hardware module at adifferent instance of time.

Hardware modules can provide information to, and receive informationfrom, other hardware modules. Accordingly, the described hardwaremodules may be regarded as being communicatively coupled. Where multipleof such hardware modules exist contemporaneously, communications may beachieved through signal transmission (e.g., over appropriate circuitsand buses) that connects the hardware modules. In embodiments in whichmultiple hardware modules are configured or instantiated at differenttimes, communications between such hardware modules may be achieved, forexample, through the storage and retrieval of information in memorystructures to which the multiple hardware modules have access. Forexample, one hardware module may perform an operation and store theoutput of that operation in a memory device to which it iscommunicatively coupled. A further hardware module may then, at a latertime, access the memory device to retrieve and process the storedoutput. Hardware modules may also initiate communications with input oroutput devices and can operate on a resource (e.g., a collection ofinformation).

The various operations of example methods described herein may beperformed, at least partially, by one or more processors that aretemporarily configured (e.g., by software) or permanently configured toperform the relevant operations. Whether temporarily or permanentlyconfigured, such processors may constitute processor-implemented modulesthat operate to perform one or more operations or functions. The modulesreferred to herein may, in some example embodiments, compriseprocessor-implemented modules.

Similarly, the methods described herein may be at least partiallyprocessor-implemented. For example, at least some of the operations of amethod may be performed by one or more processors orprocessor-implemented modules. The performance of certain of theoperations may be distributed among the one or more processors, not onlyresiding within a single machine, but deployed across a number ofmachines. In some example embodiments, the processor or processors maybe located in a single location (e.g., within a home environment, anoffice environment or as a server farm), while in other embodiments theprocessors may be distributed across a number of locations.

The one or more processors may also operate to support performance ofthe relevant operations in a “cloud computing” environment or as a“software as a service” (SaaS). For example, at least some of theoperations may be performed by a group of computers (as examples ofmachines including processors), with these operations being accessiblevia a network (e.g., the Internet) and via one or more appropriateinterfaces (e.g., APIs).

Example embodiments may be implemented in digital electronic circuitry,or in computer hardware, firmware, software, or in combinations ofthese. Example embodiments may be implemented using a computer programproduct, for example, a computer program tangibly embodied in aninformation carrier, for example, in a machine-readable medium forexecution by, or to control the operation of, data processing apparatus,for example, a programmable processor, a computer, or multiplecomputers.

A computer program can be written in any form of programming language,including compiled or interpreted languages, and it can be deployed inany form, including as a stand-alone program or as a module, subroutine,or other unit suitable for use in a computing environment. A computerprogram can be deployed to be executed on one computer or on multiplecomputers at one site or distributed across multiple sites andinterconnected by a communication network.

In example embodiments, operations may be performed by one or moreprogrammable processors executing a computer program to performfunctions by operating on input data and generating output. Methodoperations can also be performed by, and apparatus of exampleembodiments may be implemented as, special purpose logic circuitry(e.g., a FPGA or an ASIC).

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other. Inembodiments deploying a programmable computing system, it will beappreciated that both hardware and software architectures requireconsideration. Specifically, it will be appreciated that the choice ofwhether to implement certain functionality in permanently configuredhardware (e.g., an ASIC), in temporarily configured hardware (e.g., acombination of software and a programmable processor), or a combinationof permanently and temporarily configured hardware may be a designchoice. Below are set out hardware (e.g., machine) and softwarearchitectures that may be deployed, in various example embodiments.

FIG. 10 is a block diagram of a machine in the example form of acomputer system 1000 within which instructions, for causing the machineto perform any one or more of the methodologies discussed herein, may beexecuted. In alternative embodiments, the machine operates as astandalone device or may be connected (e.g., networked) to othermachines. In a networked deployment, the machine may operate in thecapacity of a server or a client machine in a server-client networkenvironment, or as a peer machine in a peer-to-peer (or distributed)network environment. The machine may be a personal computer (PC), atablet PC, a set-top box (STB), a PDA, a cellular telephone, a webappliance, a network router, switch or bridge, or any machine capable ofexecuting instructions (sequential or otherwise) that specify actions tobe taken by that machine. Further, while only a single machine isillustrated, the term “machine” shall also be taken to include anycollection of machines that individually or jointly execute a set (ormultiple sets) of instructions to perform any one or more of themethodologies discussed herein.

The example computer system 1000 includes a processor 1002 (e.g., acentral processing unit (CPU), a graphics processing unit (GPU), orboth), a main memory 1004 and a static memory 1006, which communicatewith each other via a bus 1008. The computer system 1000 may furtherinclude a video display unit 1010 (e.g., a liquid crystal displays (LCD)or a cathode ray tube (CRT)). The computer system 1000 also includes analphanumeric input device 1012 (e.g., a keyboard), a cursor control(client interface (UI) navigation) device 1014 (e.g., a mouse), a diskdrive unit 1016, a signal generation device 1018 (e.g., a speaker), anda network interface device 1020.

The disk drive unit 1016 includes a non-transitory machine-readablemedium 1022 on which is stored one or more sets of instructions and datastructures (e.g., software) 1024 embodying or used by any one or more ofthe methodologies or functions described herein. The instructions 1024may also reside, completely or at least partially, within the mainmemory 1004, static memory 1006, and/or within the processor 1002 duringexecution thereof by the computer system 1000, with the main memory 1004and the processor 1002 also constituting machine-readable media.

While the machine-readable medium 1022 is shown in an example embodimentto be a single medium, the term “machine-readable medium” may include asingle medium or multiple media (e.g., a centralized or distributeddatabase, and/or associated caches and servers) that store the one ormore instructions or data structures. The term “machine-readable medium”shall also be taken to include any tangible medium that is capable ofstoring, encoding or carrying instructions for execution by the machineand that cause the machine to perform any one or more of themethodologies of the present innovations, or that is capable of storing,encoding or carrying data structures used by or associated with suchinstructions. The term “machine-readable medium” shall accordingly betaken to include, but not be limited to, solid-state memories andoptical and magnetic media. Specific examples of machine-readable mediainclude non-volatile memory, including by way of example, semiconductormemory devices (e.g., Erasable Programmable Read-Only Memory (EPROM),Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flashmemory devices; magnetic disks such as internal hard disks and removabledisks; magneto-optical disks; and CD-ROM and DVD-ROM disks.

The instructions 1024 may further be transmitted or received over acommunications network 1026 using a transmission medium. Theinstructions 1024 may be transmitted using the network interface device1020 and any one of a number of well-known transfer protocols (e.g.,hypertext transfer protocol). Examples of communication networks includea LAN, a WAN, the Internet, mobile telephone networks, Plain OldTelephone (POTS) networks, and wireless data networks (e.g., WiFi andWiMax networks). The term “transmission medium” shall be taken toinclude any intangible medium that is capable of storing, encoding orcarrying instructions for execution by the machine, and includes digitalor analog communications signals or other intangible media to facilitatecommunication of such software.

Although an embodiment has been described with reference to specificexample embodiments, it will be evident that various modifications andchanges may be made to these embodiments without departing from thebroader spirit and scope of the embodiments described herein.Accordingly, the specification and drawings are to be regarded in anillustrative rather than a restrictive sense. The accompanying drawingsthat form a part hereof, show by way of illustration, and not oflimitation, specific embodiments in which the subject matter may bepracticed. The embodiments illustrated are described in sufficientdetail to enable those skilled in the art to practice the teachingsdisclosed herein. Other embodiments may be used and derived therefrom,such that structural and logical substitutions and changes may be madewithout departing from the scope of this disclosure. This DetailedDescription, therefore, is not to be taken in a limiting sense, and thescope of various embodiments is defined only by the appended claims,along with the full range of equivalents to which such claims areentitled.

Such embodiments of the inventive subject matter may be referred toherein, individually and/or collectively, by the term “invention” merelyfor convenience and without intending to voluntarily limit the scope ofthis application to any single invention or inventive concept if morethan one is in fact disclosed. Thus, although specific embodiments havebeen illustrated and described herein, it should be appreciated that anyarrangement calculated to achieve the same purpose may be substitutedfor the specific embodiments shown. This disclosure is intended to coverany and all adaptations or variations of various embodiments.Combinations of the above embodiments, and other embodiments notspecifically described herein, will be apparent to those of skill in theart upon reviewing the above description.

We claim:
 1. A system comprising: a hardware processor; and a memorystoring instructions that, when executed by the processor, configure thesystem to perform operations comprising: receiving bounding informationassociated with an event, the bounding information defining a geographicboundary around the event; receiving a number of client devices withinan area of the geographic boundary; receiving, from each of theplurality of client devices, interest information associated with theevent; determining an interest level based on the interest information;determining that the interest level is greater than a thresholdassociated with the number of client devices within the area of thegeographic boundary; and in response to determining that the interestlevel is greater than the threshold, causing an event application on anevent provider server to initiate the event.
 2. The system of claim 1,wherein the threshold is a dynamic threshold that dynamically changesbased on time of day.
 3. The system of claim 1, further comprising:assigning a first weight to interest information from a first clientdevice of the number plurality of client devices and a second weight,different than the first weight, to interest information from a secondclient device of the number plurality of client devices.
 4. The systemof claim 1, wherein each of the number of plurality of client devicescomprises a stand-alone application.
 5. The system of claim 3, whereinthe first weight and the second weight are based on proximity to a fixedpoint within the geographic boundary defined by the boundinginformation.
 6. The system of claim 3, wherein the first weight and thesecond weight are based on time of day.
 7. The system of claim 1,further comprising, interfacing, via the number of plurality of clientdevices, with the event provider server.
 8. A method comprising:receiving bounding information associated with an event, the boundinginformation defining a geographic boundary around the event; receiving anumber of client devices within an area of the geographic boundary;receiving, from each of the plurality of client devices, interestinformation associated with the event; determining an interest levelbased on the interest information; determining that the interest levelis greater than a threshold associated with the number of client deviceswithin the area of the geographic boundary; and in response todetermining that the interest level is greater than the threshold,causing an event application on an event provider server to initiate theevent.
 9. The method of claim 8, wherein the threshold is a dynamicthreshold that dynamically changes based on time of day.
 10. The methodof claim 8, further comprising assigning a first weight to interestinformation from a first client device of the number of plurality ofclient devices and a second weight, different than the first weight, tointerest information from a second client device of the number ofplurality of client devices, based on previous history of interactionsby the plurality of client devices.
 11. The method of claim 8, whereineach of the plurality of client devices comprises a stand-aloneapplication.
 12. The method of claim 10, wherein the first weight andthe second weight are further based on proximity to a fixed point withinthe geographic boundary defined by the bounding information.
 13. Themethod of claim 10, wherein the first weight and the second weight arefurther based on time of day.
 14. The method of claim 8, furthercomprising, interfacing, via the plurality of client devices.
 15. Anon-transitory computer-readable medium storing executable instructionsthereon, which, when executed by a processor, causes the processor toperform operations comprising: receiving bounding information associatedwith an event, the bounding information defining a geographic boundaryaround the event; receiving a number of client devices within an area ofthe geographic boundary; receiving, from each of the plurality of clientdevices, interest information associated with the event; determining aninterest level based on the interest information; determining that theinterest level is greater than a threshold associated with the number ofclient devices within the area of the geographic boundary; and inresponse to determining that the interest level is greater than thethreshold, causing an event application on an event provider server toinitiate the event.
 16. The non-transitory computer-readable medium ofclaim 15, wherein the threshold is a dynamic threshold that dynamicallychanges based on time of day.
 17. The non-transitory computer-readablemedium of claim 15, wherein the operations further comprise assigning afirst weight to interest information from a first client device of thenumber of plurality of client devices and a second weight, differentthan the first weight, to interest information from a second clientdevice of the number of plurality of client devices, based on previoushistory of interactions by the plurality of client devices.
 18. Thenon-transitory computer-readable medium of claim 15, wherein each of thenumber of plurality of client devices comprises a stand-aloneapplication.
 19. The non-transitory computer-readable medium of claim17, wherein the first weight and the second weight are further based onproximity to a fixed point within the geographic boundary defined by thebounding information.
 20. The non-transitory computer-readable medium ofclaim 15, further comprising interfacing, via the number of plurality ofclient devices.